Method and apparatus for two-phase commit in data distribution to a web farm

ABSTRACT

Various methods and apparatus for synchronizing data between members of a web farm are disclosed. The web farm may include a primary member and at least one backup member. The web farm members may include modules for determining whether new data is available to the web farm; placing the web farm in a prepare state if new data is available; placing the web farm in a commit state if members of the web farm successfully receive the new data; and placing the web farm in an abort state if any of the members of the web farm do not successfully receive the new data.

BACKGROUND

[0001] I. Field

[0002] This disclosure relates to data communication, and in particular, to a novel and improved web farm data synchronization system.

[0003] II. Background

[0004] Web farms are integral to high-volume web sites because they increase the availability of web sites by distributing processing tasks among several web farm “members.”

[0005]FIG. 1 is a schematic diagram of a prior art web farm 100 including members 1 . . . n. Each member is configured to function as a web server as is known in the art and may include a processor 102 and a database 104 for the storage and retrieval of data.

[0006] One challenge in implementing a web farm is ensuring that data files are synchronized among all members of the web farm. Typically, new data is presented simultaneously to all members of the web farm 100 through a gateway 106. For the web site to function effectively, data that is presented to the web farm must be stored within the individual members such that data integrity is maintained from member to member. For example, if the new data presented to the web farm represents a new customer to be stored in customer database, all members of the web farm must store the new customer data prior to a new transaction occurring. If any member of the web farm fails to store the new data, the integrity of any future transactions may be compromised.

[0007] The prior art has recognized the importance of data synchronization and made attempts to ensure the integrity of distributed data. For example, prior art web farms may employ a time delay to allow all members of the web farm to catch up and store the new data. However, this approach has certain disadvantages. Such a time delay necessarily imposes a limitation on the availability of the individual members of the web farm, and thus the availability of the hosted web site as whole. Furthermore, during the time delay, the new data is being stored on some members of the web farm, while the other members are catching up. Thus, the web farm is not synchronized during the time period. Should at least one of the members fail to synchronize the new data, the web farm may need to be rolled back, a process whereby the data is restored on the members to a previous known state. Rolling back a web farm is an undesirable procedure that is tedious and potentially error-prone.

SUMMARY

[0008] Methods and apparatus for synchronizing data between members of a web farm are disclosed. In one embodiment, a method includes determining whether new data is available to the web farm; placing the web farm in a prepare state if new data is available; placing the web farm in a commit state if members of the web farm successfully receive the new data; and placing the web farm in an abort state if any of the members of the web farm do not successfully receive the new data.

[0009] In a further aspect, a method for synchronizing data between members of a web farm is disclosed including instructing the members of the web farm to receive new data; determining whether any of the web farm members failed to receive the new data; instructing the web farm members to store the new data if all of the web farm members received the new data; and instructing the web farm members to revert to a previous set of data if any of the web farm members failed to receive the new data.

[0010] A synchronized web farm is also disclosed. In one aspect, the web farm may include a primary web farm member configured to receive data from an application download server; and at least one backup web farm member also configured to receive data from an application download server. The primary member may be configured to determine whether new data is available to the web farm; place the web farm in a prepare state if new data is available; place the web farm in a commit state if members of the web farm successfully receive the new data; and place the web farm in an abort state if any of the members of the web farm do not successfully receive the new data.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The features, objects, and advantages of the present invention will become more apparent from the detailed description set forth below when taken in conjunction with the drawings in which like reference characters identify correspondingly throughout and wherein:

[0012]FIG. 1 is a schematic diagram of a prior art web farm;

[0013]FIG. 2 is a schematic diagram of one aspect of a web farm configured in accordance with the teachings of this disclosure;

[0014]FIG. 3 is a schematic diagram of one aspect of a primary member configured in accordance with the teachings of this disclosure;

[0015]FIG. 4 is a schematic diagram of one aspect of a backup member configured in accordance with the teachings of this disclosure;

[0016]FIG. 5 is a schematic diagram of one aspect of a storage member configured in accordance with the teachings of this disclosure;

[0017]FIG. 6 is a flow diagram of one aspect of a web farm synchronization in accordance with the teachings of this disclosure;

[0018]FIG. 7 is a state diagram of one aspect of a web farm synchronization in accordance with the teachings of this disclosure; and

[0019]FIG. 8 is a schematic diagram of one aspect of a web farm featuring fail-over support in accordance with the teachings of this disclosure.

DETAILED DESCRIPTION

[0020] Persons of ordinary skill in the art will realize that the following description of the present invention is illustrative only and not in any way limiting. Other embodiments of the invention will readily suggest themselves to such skilled persons having the benefit of this disclosure.

[0021] It is contemplated that the present invention may be embodied in various computer and machine readable data structures. Furthermore, it is contemplated that data structures embodying the present invention will be transmitted across computer and machine-readable media, and through communications systems by use of standard protocols known in the art.

[0022] The invention further relates to machine-readable media on which are stored embodiments of the present invention. It is contemplated that any media suitable for storing instructions related to the present invention is within the scope of the present invention. By way of example, such media may take the form of magnetic, optical, or semiconductor media.

[0023] The present invention may be described through the use of flowcharts. Often, a single instance of an embodiment of the present invention will be shown. As is appreciated by those of ordinary skill in the art, however, the protocols, processes, and procedures described herein may be repeated continuously or as often as necessary to satisfy the needs described herein. Accordingly, the representation of the present invention through the use of flowcharts should not be used to limit the scope of the present invention.

[0024] Exemplary embodiments of disclosed apparatus and methods may be disclosed herein. The word “exemplary” is used exclusively herein to mean “serving as an example, instance, or illustration.” Any embodiment described as an “exemplary embodiment” is not to be construed as necessarily preferred or advantageous over other embodiments described herein.

[0025] Exemplary Structure

[0026]FIG. 2 is a schematic diagram of a web farm 200 configured in accordance with the teachings of this disclosure. The web farm 200 may include a primary member 202 and at least one backup member 204, each configured as will be described in more detail below. The web farm may also include at least one storage member 206.

[0027] It is contemplated that the various members of the web farm may include hardware and software known in the art for running an operating system such as Microsoft Windows®, UNIX, LINUX, or any other desired operating system, and are preferably configured to run applications written in the Java language. A member machine may comprise may comprise a stand-alone computer, a multi-CPU machine, or a rack-mounted server housed together with other servers on a rack.

[0028] The members of the web farm 200 may also be configured to administrate a database such as Oracle® using hardware and software as is known in the art. In a exemplary embodiment, the members of the web farm 200 may be configured to store and retrieve data received in the Extended Markup Language (XML) format.

[0029] The members of the web farm 200 are preferably configured to receive data from a Distribution Server 300. The DS 300 may be configured to function as a transaction gateway between the web farm 200 and the internal network of the enterprise hosting the web farm. To provide secure transaction capability, the web farm 200 and the DS 300 may communicate through a firewall 302 using secure protocols known in the art, such as SSL over VPN.

[0030] Each member of the web farm 200 will now be disclosed in more detail.

[0031] Primary Member

[0032] In the web farm 200 of the present disclosure, it is contemplated that there will be one primary member 202 that is responsible for the synchronization of the various members of the web farm. As every farm member in the web farm should represent the data state, the primary member 202 functions as a distribution manager and ensures that all members of the web farm have the data set. In an exemplary embodiment, the primary member 202 ensures that all members have the same XML and application package files at any given time.

[0033]FIG. 3 shows a functional block diagram of a primary member 202 configured in accordance with the teachings of this disclosure. The primary member 202 includes a primary synchronization manager (SyncMgr) module 302 for controlling the scheduling and the synchronization of all data, such as XML and package files, in each web farm member. The SyncMgr module 302 may be programmed as a Java application. The SyncMgr module may run on each of the web farm machines using separate Java Virtual Machines for reliability. The primary SyncMgr 302 may also be operatively coupled to other members of the web farm 200 to provide primary synchronization control as will be described in more detail below.

[0034] The primary manager 202 may also include an Application Download Client (AdaClt) module 304 for downloading data from the DS 300 of FIG. 2. The AdaClt module 304 preferably communicates with the DS 300 through the firewall 302 via HTTPS to receive data, such as XML and package files. The AdaClt module 304 may be programmed as a Java application.

[0035] The primary manager 202 may also include a Distribution Client (DistClt) servlet 306 for interfacing with the AdaClt module 304. The DistClt servlet 306 may used by the web farm members to activate the AdaClt 304 to initiate the download process and download data to a database 308. The DistClt servlet 306 may comprise a Java servlet engine configured to start up at boot time.

[0036]FIG. 4 shows a functional block diagram of a backup member 204 configured in accordance with the teachings of this disclosure. The backup member 204 also includes a SyncMgr module 402 as described above. However, the backup SyncMgr 402 is preferably operatively coupled to other members of the web farm 200 to provide backup synchronization control as will be described in more detail below.

[0037] The backup member 204 may also include an AdaClt module 304 and a DistClt servlet 306 as described above for receiving data from the DS 300. The backup module 204 also includes a database 308 for the storage and retrieval of data received from the DS 300, and is preferably configured to store data received from the DS 300 under the control of the primary member 202.

[0038]FIG. 5 shows a functional block diagram of a storage member 206 configured in accordance with the teachings of this disclosure. The storage member 206 is preferably configured to store data received from the DS 300 under the control of the primary member 202.

[0039] The storage member 206 may include an AdaClt module 304, a DistClt servlet 306, and a database 308 as described above.

[0040] Various aspects of operation for a web farm of this disclosure will now be disclosed.

[0041] Operation

[0042] The SyncMgr module is configured to implement a two-phase commit algorithm to ensure members of the web farm receive new data from the distribution center at the same time.

[0043]FIG. 6 is a flowchart of one aspect of data synchronization in accordance with the teachings of this disclosure. The process of FIG. 6 begins in act 600, where the members of the web farm are instructed to get new data. In one aspect of this disclosure, this act may be accomplished by a primary member instructing the other members of the web farm to fetch data from an distribution server.

[0044] The process continues in query 602, where it is determined whether any web farm members failed in their attempt to receive the new data. If none of the web farm members failed to receive the new data, the web farm members may be instructed to store the new data in act 604.

[0045] However, if any of the web farm members failed to properly receive the new data, all members of the web farm may be instructed to revert back to the previous data set in act 606. Thus, if any member of the web farm is unable to properly receive the new data, all web farm members may revert back to the existing data set.

[0046] Hence, the process of FIG. 6 ensures that either all of the web farm members receive the new data, or, if any one of the web farm members fails to receive the new data, none of the web farm members use the new data. Thus, the process of FIG. 6 may eliminate any data inconsistencies between web farm members.

[0047]FIG. 7 is a state diagram of a further aspect of data synchronization in accordance with the present disclosure. The process of FIG. 7 begins when the web farm is placed in a prepare state. In one aspect, the primary member as disclosed above may function as a distribution manager by requesting each web farm member to download or receive data from a distribution center. It is contemplated that the distribution manager may periodically check for new data. When new data is available, the distribution manager may then place the web farm in a prepare state.

[0048] During the prepare state, it is contemplated that each web farm member may store newly received data in a temporary repository, such as a new database file.

[0049] While still in the prepare state, each web farm member may notify the distribution manager of the storage state of the new data, i.e., whether their respective receive process was successful or not. It is contemplated that the distribution manager may wait a predetermined time for all web farm members to respond during the prepare state.

[0050] If all web farm members respond with an indication that new data has been successfully stored, the web farm may then move to a commit state. In the commit state, the distribution manager may request the web farm members to make the new data their permanent data. This may be accomplished by the distribution manager requesting that newly-stored data in a temporary repository be made the current data.

[0051] If any of the web farm members indicate that the new data was not stored successfully, the web farm may be placed in an abort state. In the abort state, the distribution manager may implement a rollback action in which the prepare state is aborted and the temporary data is not made the current data. Additionally, if any of the web farm members fail to respond in a predetermined amount of time, the distribution manager may determine that the prepare state has timed out, and place the web farm in the abort state.

[0052] The web farm of the present disclosure may also provide fail-over support in case the primary member fails. FIG. 8 is a block diagram of a web farm 800 configured to provide fail-over support in accordance with the teachings of this disclosure. FIG. 8 includes a primary member 202 and one or more backup members 204, each configured substantially as shown and described above.

[0053]FIG. 8 further shows that the SyncMgrs of the primary and backup members may be operatively coupled to provide fail-over support. As disclosed above, there is only one primary SyncMgr 202 in the web farm, but there may be one or more backup SyncMgrs 204. The identity of the primary SyncMgr may be predetermined through methods such as hardwiring or preprogramming, thereby ensuring that a primary web farm member exists at start-up.

[0054] One of the backup members 204 may be configured to watch over the primary member 202. In an exemplary embodiment, the SyncMgr module of the backup member 204 may periodically check to ensure the primary manager 202 is available. If the backup member 204 determines that the primary member 202 is not available, the backup manager 204 may conclude that the primary manager 202 has failed. In a further exemplary embodiment, a backup manager may make a predetermined number of consecutive unsuccessful attempts before concluding that the primary manager has failed.

[0055] In the event of the failure of the primary member, a backup manager may assume control of the web farm by becoming the primary member.

[0056]FIG. 8 further shows that in the case where there is a plurality of backup members, the backup members may be configured to watch over each other in a chain of N members, where N is the number of backup members present in the web farm. In the event of multiple failures, the next backup member in line will assume the role of the primary member. Thus, the web farm of the present disclosure provides N+1 levels of redundancy, including the initial primary manager.

[0057] In an exemplary embodiment, the order of the hostnames recorded in a configuration file may determine which backup SyncMgr will take over the primary duty.

[0058] Additionally, various site-specific information may be contained in configuration files for use by the modules of the disclosed web farm.

[0059] The previous description of various embodiments, which include preferred embodiments, is provided to enable any person skilled in the art to make or use the embodiment of the present disclosure. The various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without the use of the inventive faculty. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. 

What is claimed is:
 1. A method for synchronizing data between members of a web farm comprising: determining whether new data is available to the web farm; placing the web farm in a prepare state if new data is available; placing the web farm in a commit state if all members of the web farm successfully receive said new data; and placing the web farm in an abort state if any of said members of said web farm do not successfully receive said new data.
 2. The method of claim 1, wherein said act of determining whether new data is available to the web farm is performed periodically.
 3. The method of claim 1, wherein said act of placing the web farm in a prepare state further includes the act of placing, by said web farm members, said new data in a temporary repository.
 4. The method of claim 1, wherein said act of placing the web farm in a prepare state further includes the act of notifying, by said web farm members, a distribution manager of the storage state of said new data.
 5. The method of claim 4, wherein said act of placing the web farm in a prepare state further includes the act of waiting, by said distribution manager, a predetermined time to received said storage state notifications.
 6. The method of claim 3, wherein said act of placing the web farm in a commit state further includes the act of making said temporary repository data said web farm's current data.
 7. The method of claim 1, wherein said act of placing the web farm in an abort state further includes the act of implementing a rollback action.
 8. The method of claim 1, further including the act of providing, by said web farm members, fail-over support for a primary member.
 9. The method of claim 8, further including the act of periodically checking, by said web farm members, the availability of said primary member.
 10. The method of claim 9, further including the act of assuming control, by a predetermined web farm member, of said web farm if said primary member is not available.
 11. The method of claim 9, wherein said predetermined web farm member checks the availability of said primary member a predetermined number of times before assuming control.
 12. The method of claim 10, wherein said web farm members assume control in a predetermined order.
 13. A method for synchronizing data between members of a web farm comprising: providing a primary member and at least one backup member; instructing the members of the web farm to receive new data; determining whether any of said web farm members failed to receive said new data; instructing said web farm members to store said new data if all of said web farm members received said new data; and instructing said web farm members to revert to a previous set of data if any of said web farm members failed to receive said new data.
 14. The method of claim 13, wherein said act of instructing the members of the web farm to receive new data further includes the act of placing said new data in a temporary repository.
 15. The method of claim 13, wherein said act of instructing the members of the web farm to receive new data further includes the act of notifying, by said at least one backup member, said primary member of the storage state of said new data.
 16. The method of claim 15, wherein said act of instructing the members of the web farm to receive new data further includes the act of waiting, by said primary member, a predetermined time to received said storage state notifications.
 17. The method of claim 14, wherein said act of instructing said web farm members to store said new data further includes the act of making said temporary repository data said web farm's current data.
 18. The method of claim 13, further including the act of providing, by said at least one backup member, fail-over support for a primary member.
 19. The method of claim 18, further including the act of periodically checking, by said at least one backup member, the availability of said primary member.
 20. The method of claim 9, further including the act of assuming control, by a predetermined backup member, control of said web farm if said primary member is not available.
 21. The method of claim 9, wherein said predetermined backup member checks the availability of said primary member a predetermined number of times before assuming control.
 22. The method of claim 10, wherein said at least one backup members assume control in a predetermined order.
 23. A synchronized web farm comprising: a primary web farm member configured to receive data from an distribution server at least one backup member configured to receive data from a distribution server; and wherein said primary member is configured to: determine whether new data is available to the web farm; place the web farm in a prepare state if new data is available; place the web farm in a commit state if members of the web farm successfully receive said new data; and place the web farm in an abort state if any of said members of said web farm do not successfully receive said new data.
 24. The web farm of claim 23, wherein said primary member is further configured to determine whether new data is available to the web farm is performed periodically.
 25. The web farm of claim 23, wherein said web farm members are further configured to store said new data in a temporary repository.
 26. The web farm of claim 23, wherein said at least one backup member is further configured to notify said primary member of the storage state of said new data.
 27. The web farm of claim 26, wherein said primary member is further configured to wait a predetermined time to received said storage state notifications.
 28. The web farm of claim 23, wherein said web farm is further configured to implement a rollback action in the event of said abort state.
 29. The web farm of claim 23, wherein said web farm is further configured to provide fail-over support for said primary member.
 30. The web farm of claim 29, wherein said web farm is further configured to periodically check the availability of said primary member.
 31. The web farm of claim 30, wherein said web farm is further configured to assuming control, by a predetermined web farm member, of said web farm if said primary member is not available.
 32. The web farm of claim 31, wherein said predetermined web farm member is further configured to check the availability of said primary member a predetermined number of times before assuming control.
 33. The web farm of claim 31, wherein said web farm members are further configured to assume control in a predetermined order.
 34. A system for synchronizing data between members of a web farm comprising: means for determining whether new data is available to the web farm; means for placing the web farm in a prepare state if new data is available; means for placing the web farm in a commit state if all members of the web farm successfully receive said new data; and means for placing the web farm in an abort state if any of said members of said web farm do not successfully receive said new data.
 35. The system of claim 34, further including means for determining whether new data is available to the web farm is performed periodically.
 36. The system of claim 34, further including means for placing the web farm in a prepare state further includes the act of placing, by said web farm members, said new data in a temporary repository.
 37. The system of claim 34, further including means for notifying, by said web farm members, a distribution manager of the storage state of said new data.
 38. The system of claim 37, f further including means for waiting, by said distribution manager, a predetermined time to received said storage state notifications.
 39. The system of claim 36, further including means for making said temporary repository data said web farm's current data.
 40. The system of claim 34, further including means for implementing a rollback action.
 41. The system of claim 34, further including means for providing, by said web farm members, fail-over support for a primary member.
 42. The system of claim 41, further including means for periodically checking, by said web farm members, the availability of said primary member.
 43. The system of claim 42, further including means for assuming control, by a predetermined web farm member, of said web farm if said primary member is not available.
 44. The system of claim 43, further including means for checking the availability of said primary member a predetermined number of times before assuming control.
 45. The system of claim 43, further including means for assuming control in a predetermined order.
 46. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a method for synchronizing data between members of a web farm, said method comprising: determining whether new data is available to the web farm; placing the web farm in a prepare state if new data is available; placing the web farm in a commit state if all members of the web farm successfully receive said new data; and placing the web farm in an abort state if any of said members of said web farm do not successfully receive said new data.
 47. The program storage device of claim 46, wherein said act of determining whether new data is available to the web farm is performed periodically.
 48. The program storage device of claim 46, wherein said act of placing the web farm in a prepare state further includes the act of placing, by said web farm members, said new data in a temporary repository.
 49. The program storage device of claim 46, wherein said act of placing the web farm in a prepare state further includes the act of notifying, by said web farm members, a distribution manager of the storage state of said new data.
 50. The program storage device of claim 49, wherein said act of placing the web farm in a prepare state further includes the act of waiting, by said distribution manager, a predetermined time to received said storage state notifications.
 51. The program storage device of claim 48, wherein said act of placing the web farm in a commit state further includes the act of making said temporary repository data said web farm's current data.
 52. The program storage device of claim 46, wherein said act of placing the web farm in an abort state further includes the act of implementing a rollback action.
 53. The program storage device of claim 46, further including the act of providing, by said web farm members, fail-over support for a primary member.
 54. The program storage device of claim 53, further including the act of periodically checking, by said web farm members, the availability of said primary member.
 55. The program storage device of claim 54, further including the act of assuming control, by a predetermined web farm member, of said web farm if said primary member is not available.
 56. The program storage device of claim 54, wherein said predetermined web farm member checks the availability of said primary member a predetermined number of times before assuming control.
 57. The program storage device of claim 56, wherein said web farm members assume control in a predetermined order. 